dl-breadcrumbs__homedl-breadcrumb-item__separatorConfiguration and programmingdl-breadcrumb-item__separatorProgramming with CODESYSdl-breadcrumb-item__separator...dl-breadcrumb-item__separatorCODESYS Visualizationdl-breadcrumb-item__separatorReference: User Interface dl-breadcrumb-item__separatorObjects dl-breadcrumb-item__separatorObject: Trend Recording
dl-pagination__prev-inactivedl-pagination__prev-activedl-pagination__next-inactivedl-pagination__next-active
Object: Trend Recording dl-permalink__symbolPermalink

Symbol: _visu_icon_trend_recording.png

NOTICE

NOTICE
NOTICE
NOTICE

NOTICE

NOTICE

Timeout for trend recording

During a trend recording, it can happen that the application task triggers a timeout that is caught with an exception when transitioning from “Running” to “Stop”. Causes can be that file operations with the SQLite database are taking too long or that too many variables are being recorded. This usually happens on a target device with weak performance.

You can avoid the occurrence of an exception:

  • Configure the trend recording with less memory demand so that the amount of data that is stored is adapted to the target system.

  • Reduce the number of variables.

In a trend recording, you configure which data is recorded, where, and in which time interval.

At runtime, CODESYS TargetVisu transfers the configuration to the ‎CmpTraceMgr‎ runtime system component.

  • Group: “Record Settings”
  • Group: Variable Settings